|
TNAPS is a freeware .NET cross-platform application server for .NET, Mono, and Java, with component-driven architecture. It is based on the concept of application business logic separation into middleware layer. This is also called three-tier software architecture. Although there are many application servers for Java platform, there are no cross-platform application servers for .NET and Mono. The main principle of TNAPS is that a developer has to write business logic only and would be able to host it and set user access policy, database parameters and other configuration without writing code – just by existing component reusage. Current version of TNAPS requires .NET 4 (Windows) and Mono 2.10.1 (Linux and Mac OS X) == Basics == TNAPS focuses on business logic implementation. Developer applies principle of decomposition and splits server side logic into set of components (called ''business objects'' in TNAPS). The main idea behind this decomposition is to get business objects that provide some ''value'' to the end-user (the one using client application). Developer defines business objects ''contracts'' for accessing created server functionality and implement client application using contracts. After finishing set of business objects development they should be arranged into ''Bizlet'' - one server application instance in TNAPS. Bizlet contains business objects, database configuration, user access permissions and hosting parameters (i.e. IP address and port to listen). Developers or end-users of the TNAPS application can decide what kind of logic provide to the respective use by granting or revoking access to particular business object. Business objects access permissions are defined at the user group level. 抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)』 ■ウィキペディアで「TNAPS Application Server」の詳細全文を読む スポンサード リンク
|